home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
gt_power
/
czc030.zip
/
CZ_CHECK.DOC
next >
Wrap
Text File
|
1990-12-01
|
5KB
|
158 lines
┌──────────┐
│ CZ_CHECK │
└──────────┘
Rev 0.3 1st Dec 1990
--------------------
Rev 0.2 was double-spacing the text of any .MES file that it fixed.
This revision corrects that, and also another problem which could cause an
'unable to malloc' error when processing multiple message bases.
Rev 0.2 29th Nov 1990
---------------------
Revised so it can FIX as well as find ...
Instead of the optional command, use the keyword FIX on the command line,
eg
cz_check 5 @c:\gt\gtmdir.bbs fix
which will find and fix all .MES files containing ^Z in the message
bases listed in the specified gtmdir.bbs filw.
- - -
CZ_CHECK is a program for GT16 beta testers - it checks message bases to
see if any recently-updated .MES files contain ^Z characters.
These can cause problems with some companion programs, which are likely to
be fixed in the near future, but this will help you keep the message base
clean until that happens.
You can either :
a) just display the .MES file name,
b) execute your editor with the offending file, or
c) strip out the ^Z characters.
┌─────────────┐
│ The Command │
└─────────────┘
For a single message base :
┌──────────────────────── age limit, in days
│ ┌──────────────── the message base directory
│ │ ┌───────── (optional) command to execute
┴ ──────┴───── ┴ if ^Z found
cz_check 5 d:\msgs\ansi q
For multiple message bases :
┌───────────────────────────── age limit, in days
│ ┌───────────────────── a gtmdir file
│ │ ┌───────── (optional) command to execute
┴ ──────┴────────── ┴─── if ^Z found
cz_check 5 @c:\gt\gtmdir.bbs edit
To FIX a message base, use the word FIX in place of the command, eg
cz_check 5 @c:\gt\gtmdir.bbs fix
┌───────────┐
│ Age Limit │
└───────────┘
The age limit restricts checking to .MES files that have been created
or updated withing the specified number of days. This should catch
all new messages *and* any edited messages.
First time, run with a large number, eg 90 days. This should find any
problems, however old they may be.
Subsequently, you can save time by specifying a short period, eg 3 days.
If you're running it every day that will save some time.
Nominally, 0 means "any time today", 1 means "since yesterday morning",
etc. But please allow for the possibility that timezones may interfere
with things. If in doubt, add a day or two.
Important: If you find anything that manages to update a .MES file
(apart from direct access by a disc maintenance program)
*without* changing its time and date, please let me know -
that would really screw things up in a shared environment !
┌───────────────────┐
│ Message Base Spec │
└───────────────────┘
As the examples show, this can either be
a) the name of a single message base directory, or
b) an @ followed by the full path to a gtmdir.bbs file, in which case
all message bases listed in that gtmdir.bbs file will be checked
sequentially.
┌──────────────────┐
│ Optional Command │
└──────────────────┘
The command, if used, would normally be the name of a convenient editor,
which would be executed along with the name of the offending .MES file, so
that you can correct the error.
If the optional command is not specified, errors will simply be displayed.
You may find it convenient to run with CONCOPY to save the output, or
just redirect to a file by
cz_check params.... > cz.out
If you want to FIX any errors, put FIX in place of the command name.
┌─────────────────┐
│ Using an Editor │
└─────────────────┘
If you are using an editor to fix the files, you'd better check that it
doesn't discard information after a ^Z. Some of the problem files contain
the ^Z in the middle of the file rather than at the end.
Also, check it isn't configured to *add* ^Z to files it saves. Not much
point in editing them out if the editor's going to put one back!
In Qedit, you can search for a ^Z within the body of a file, using CTRL-P
CTRL-Z (which displays as a right arrow) in the search field.
Note also that Qedit will not *show* you a ^Z at the end of the file. If
you can't find a ^Z in the body of the file, force a resave with ESC-F-S
which should save the file without the ^Z. (To prove it, run cz_check
again).
┌──────────────┐
│ About FIXing │
└──────────────┘
In most cases, the automatic fix will be all that is needed.
The assumption is that the ^Z characters should NOT have been in
the file, but all else is in proper order. The file is simply rewritten,
omitting any ^Z characters that are found.
Harry Green 050/003
29th November 1990.